test(replay): [Data Collection 16] Keep Replay independent - #5832

PR Stack (Data Collection)

• feat(core): Data Collection #5759
• feat(core): [Data Collection 1] Add configuration types #5760
• feat(core): [Data Collection 2] Expose SentryOptions API #5761
• feat(core): [Data Collection 3] Add policy resolver #5799
• feat(graphql): [Data Collection 4] Apply GraphQL policies #5800
• feat(database): [Data Collection 5] Apply query policy #5801
• feat(spring): [Data Collection 6] Apply incoming request body policy #5802
• feat(apollo): [Data Collection 7] Apply incoming response body policy #5803
• feat(apollo): [Data Collection 8] Apply outgoing request body policy #5804
• feat(graphql): [Data Collection 9] Apply outgoing response body policy #5805
• feat(http): [Data Collection 10] Apply request header policy #5806
• feat(http): [Data Collection 11] Apply response header policy #5807
• feat(http): [Data Collection 12] Apply query parameter policy #5810
• feat(http): [Data Collection 13] Apply cookie collection policy #5811
• feat(user): [Data Collection 14] Apply user information policy #5812
• fix(android): [Data Collection 15] Scope device info cache to SDK options #5831
• test(replay): [Data Collection 16] Keep Replay independent #5832
• fix(android): [Data Collection 17] Apply user info policy to distinct ID #5833
• fix(spring): [Data Collection 18] Bind key-value policies #5834
• fix(android): [Data Collection 19] Preserve installation ID #5937
• fix(ktor): [Data Collection 20] Exclude query parameters from span descriptions #5983
• fix(opentelemetry): [Data Collection 21] Exclude queries from span descriptions #5985

📜 Description

Keep Session Replay network privacy settings independent from Data Collection.

Add regression coverage proving that restrictive Data Collection body and header settings do not affect explicitly enabled Replay network details. Replay continues to use its existing URL allow/deny lists, body capture option, and request/response header allow lists.

💡 Motivation and Context

sendDefaultPii has no effect on Session Replay today. Wiring Data Collection into Replay would introduce new behavior and combine controls with opposing defaults: Replay network details are opt-in through URL allow lists, while Data Collection uses its own defaults for supported integrations.

Keeping the features independent avoids privacy-sensitive behavior changes for existing Replay users. The Data Collection documentation will call out that Replay remains governed by Replay-specific options.

Refs #5666

💚 How did you test it?

• ./gradlew :sentry-okhttp:test --tests='io.sentry.okhttp.SentryOkHttpInterceptorTest'
• ./gradlew spotlessApply apiDump
• git diff --check

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Document that Session Replay is not controlled by Data Collection and continues to use Replay-specific privacy options.

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.